Contents
wcServer

Overview

Starting wcServer

Stopping wcServer

Loading wcServer and wcOnline automatically when you turn on your PC


Overview

The Bulletin Board System arena is the latest market segment to be courted by advertisements touting the benefits of “client/server” technology.  However, upon closer inspection, “client/server” is often used to refer to the use of a proprietary remote program (the client) to dial into a DOS-based BBS application (the server). While the use of a remote graphic client is an exciting aspect of many of the newer BBS technologies including Wildcat! 5, it does not represent true client/server functionality at the application program level, the location where its true power can be unleashed.

So What is Client/Server?

Client/server at its simplest level is an architecture that involves client processes requesting service from server processes.  Client/server computing recognizes that those client modules need not all be executed within the same memory space, that is, the processes that distribute the information need not all be a part of the same single program.

This is a perfect model for constructing the ideal BBS. By implementing a BBS with a core information server, and routing that information using a number of application clients at the sysop’s location, a true distributed processing system can be established that delivers more information at greater speed, even on a single PC running Windows 95.

Isn’t It Complicated?

Client/server can be as simple as running two or three familiar programs on a single PC or as intricate as a multiple-PC network running several applications on each PC. The beauty of client/server model is that once you understand the relationship between the different executable programs (the clients and the servers) you can set it up in any of several ways that best meet your needs.

The client/server model of Wildcat! 5 is a simple setup with the server and all clients running on a single PC. The computer can operate under Windows 95 or Windows NT Workstation or Server. This configuration offers the most compact system and allows for total management from the single BBS computer.

An alternative to operating all client executables on a single PC makes use of the ‘named pipes’ capability of Windows NT to allow client/server communication between multiple computers in a Microsoft NT network. The server executable runs on the Windows NT computer while the client modules can be run on either the server or networked PCs running either Windows 95 or Windows NT.

The advantage of separating some client operations from the server is increased power through distributed processing.  For example, in an extremely active system the sysop may find it advantageous to establish three workstations, each running a copy of the Modem Controller Client with its own rack of 32 modems. Another PC might be set up to handle all client activity for TCP/IP connectivity, including WWW access.

The client/server model provides a number of advantages:

•	32-bit Windows multitasking means no additional multitasking software is needed and 16-32 lines can be run easily  without loading multiple copies of the BBS.

•	The entire BBS configuration in our client/server model can be modified even while in full operation, but only by authorized personnel. The system server accepts change requests and implements them as soon as usage permits.

•	The number of inbound sessions on a single computer is significantly increased. Thanks to the enhanced multitasking of both 32-bit Windows platforms, a much larger number of connections is possible on any given PC. As inbound access (via modem, telnet, http, etc.) reaches the processor limits for any given PC, additional client PCs can be added which communicate automatically with the server. Clients for modems, http, telnet and other activities can be operated on a single PC or on a variety of additional systems, depending on load.

•	This new generation BBS can truly isolate the core of the host activities, providing secure, private system access even to local users. The server portion of the system is established in an area on disk with very limited user access.  The server controls all access to messages, files and other system information. Requests are submitted to the server by all support programs and third-party utilities through an easily adopted application program interface. This methodology has the added advantage of allowing the actual BBS operating code to be written in wcCode and to be fully customizable.

True Client/server technology provides total flexibility.  It allows the sysop to offer a BBS on a desktop platform and to expand the system capabilities as desired.


Starting wcServer

wcServer must be running in order for any other Wildcat! operations to take place, with only one exception - you cannot run wcRepair while wcServer is running, because wcRepair requires exclusive access to your Wildcat! databases in order to repair them.

•	You can only run one copy of wcServer at a time.

•	wcServer always runs minimized. You cannot zoom the icon up to a window or full screen.

To run wcServer,

1.   Open an MS-DOS prompt

2.   Change to your WILDCAT home directory (normally C:\WC5) by typing

C: [Enter]

CD \WC5 [Enter]

3.   Then type

START WCSERVER [Enter]

The Wildcat! Server icon will appear on your Task Bar (Windows 95) or Desktop (Windows NT).


Stopping wcServer

To stop wcServer,

1.   Close any other Wildcat! applications that are running.

2.   Move your mouse pointer to the Wildcat! Server icon on the Task Bar (Windows 95) or Desktop (Windows NT).

3.   Click the mouse button to pop up a menu.

4.   Select Close from the popup menu.


Loading wcServer and wcOnline automatically when you turn on your PC

How you load wcServer depends on the platform you are using.

Windows 95, no network

Windows 95, with Windows network only

Windows 95, with Novell NetWare or other networks


Windows 95, no network

You can auto-start applications such as wcServer automatically, by creating shortcut icons to these programs, and placing these shortcuts in your Startup folder. This is a simple way to ensure that your BBS will be on line and ready for calls a few moments after the PC is turned on.

However, there are some issues to consider when setting up Wildcat! this way.

Windows 95 will not auto-start applications if a Windows password is required —  until a user enters a password, no applications will be executed. Obviously, this is not what you want if your BBS must be able to start up without operator intervention.

And, since automatic startup requires you to disable logon passwords for your PC, you must carefully weigh the security issues involved.

This type of setup is appropriate only your BBS machine is located in a supervised area, where you can physically control access, such as your office, or a spare bedroom. If additional security is required, or if your BBS machine is located in an area where people can access it without supervision, additional security measures may be required,

First, let's turn off your Windows password.

•	Open your Control Panel and select the Passwords icon.

•	Double-click to pop up the Passwords Property Sheet.

•	On the "Change Passwords" tab, select "Change Windows Password".

•	In the dialog box that pops up, enter your current Windows password, if you have one.

•	Leave the New Password field blank, and press OK.

•	Next, select User Profiles, and select "All users on this PC use the same preferences".

•	Close the Passwords property sheet.

To start a wcServer and wcOnline each time Windows starts

1.   Click Start, and then point to Settings.

2.   Click Taskbar, and then click the Start Menu Programs tab.

3.   Click Add, and then click Browse.

4.   Locate the WCSERVER.EXE icon in your Wildcat!, and then double-click it.

5.   Click Next, and then double-click the StartUp folder.

6.   Type the name that you want to see on the StartUp menu, and then click Finish.

7.   If Windows prompts you to choose an icon, click one, and then click Finish.

8.   Repeat the procedure to add WCONLINE.EXE to your Startup folder.


Windows 95, with Windows network only

Windows 95 is not able to start applications automatically until after the user logs onto the network and enters a password. In some cases, it is possible to eliminate the password prompt, and start up Wildcat! by creating shortcut icons for wcServer and wcOnline in the Startup folder.

To start Windows without verifying your logon to a network:

1.   Open the Control Panel.

2.   Select Networks. Select the Configuration tab.

3.   In the Primary Network Logon list, click the down arrow, and then click Windows Logon.

No error messages will appear if you cannot be logged on to the network.


Windows 95, with Novell NetWare or other networks

No auto-start of Wildcat! is possible under these conditions, without disabling network logons. If this is a critical requirement, consider upgrading to Windows NT Workstation or Windows NT Server, which provide for automatic loading of applications (called "services") without requiring network logon.


Checking the status of the server

1.   When wcServer is running, an icon is present on the taskbar.

2.   Right click on the icon and select Status. A status property page appears.

3.   You can view the server version, server up time, and CPU time.


Troubleshooting

If you try to start a Wildcat! support program, such as wcConfig, without the server running, you’ll get a message saying that no Wildcat server was found.

If you shut down the server while something is still using it, any programs using the server will terminate abnormally with Windows exception errors.

Whenever I attempt to start wcServer, Windows tries to dial my ISP.

The various WC5 modules use TCP/IP to communicate with wcServer. One of your existing Internet applications is configured to dial your provider when TCP/IP is requested, and you’ll need to disable the AUTODIAL feature in this application.

My WC5 programs can’t find wcServer, yet wcServer is running.

Make sure both PCs are in the same Windows workgroup (or DOMAIN, in the case of NT), and the TCP/IP protocol is installed.

Windows 95: From Control Panel, click on Network/Client for Microsoft networks/Properties, and the field is Windows NT domain.

NT: The domain info is displayed in the Control Panel under Network.

wcServer starts and can’t initialize LRPC.

LRPC stands for Local Remote Procedure Call. This error can occur if the server does not exit properly. Restart Windows to correct the problem.

Can I run the WC5 modules across a Windows network?

Yes. There are three requirements to do so.

1.   Both machines must be in the same workgroup (Windows 95) or workgroup or domain (NT) for the network.

2.   Both machines must have a unique IP address. Example: machine #1= 10.0.0.1 machine #2= 10.0.0.2 machine #x= 10.0.0.x

3.   Start wcServer . Go to machine number x and start wcConfig (or wcOnline or wcLocal etc.). Choose the preferred server.


Close
Closes wcServer, canceling any current connections.


OK-
Closes the wcServer status box.


Refresh-
 Refreshes all information in the wcServer  status screen.


Server CPU time
  Displays the speed of the CPU currently running.


Server up time
  Displays the amount of time that the server has been running during the current session.


Server
Displays the version of the server currently running.


Status
Pops up the wcServer status display box.